Skip to content

docs: recommend parallel test execution - #1917

Open
harshit-s-gowda wants to merge 1 commit into
python:mainfrom
harshit-s-gowda:gh-1895-parallel-testing
Open

harshit-s-gowda wants to merge 1 commit into
python:mainfrom
harshit-s-gowda:gh-1895-parallel-testing

Conversation

@harshit-s-gowda

Copy link
Copy Markdown

Summary

  • Recommend parallel test execution with -j0 in the main test-running examples.
  • Apply the recommendation to Unix, macOS, and Windows commands.
  • Remove the duplicate parallel-testing section.

Issue

Closes #1895

@python-cla-bot

python-cla-bot Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

All commit authors signed the Contributor License Agreement.

CLA signed

@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 CPython devguide | 🛠️ Build #34917804 | 📁 Comparing 7466a23 against latest (2439c5f)

  🔍 Preview build  

1 file changed
± testing/run-write-tests/index.html

In other words: if some module does not have ``unittest.main()``, then
most likely it does not support direct invocation.

If you have a multi-core or multi-CPU machine, you can enable parallel testing

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add a section expanding how to run tests not in parallel?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To run tests sequentially, omit -j0 from the command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Devguide recommends a very slow testing configuration

3 participants